Life tag testing

[dvgrn]

Am I imagining things, or are ZOOM waypoints not interpolating right in Build 239?

I'll go look up the standard test cases for LINEAR and BEZIER and see if I'm doing something wrong. Some of this syntax just doesn't seem to stick in my head very well.

EDIT: Here's a version closer to my original version, with some more attempts to fix the problem by adding an initial zoom level and LINEAR ZOOMs here and there, but the lack of interpolation still seems to be happening:

Code: Select all

x = 25, y = 25, rule = B3/S23:P25,25
$8b2o$7b2o$8b2o$9bo!
#C [[ AUTOFIT AUTOFIT OFF STARS STARS OFF THUMBLAUNCH HISTORYFIT HISTORYFIT OFF STATE1FIT STATE1FIT OFF ]]

Also, STOP and LOOP commands at the end of a series of waypoints seem to be not working, unless I'm doing something else wrong.

[rowett]

Am I imagining things, or are ZOOM waypoints not interpolating right in Build 239?

I'll go look up the standard test cases for LINEAR and BEZIER and see if I'm doing something wrong. Some of this syntax just doesn't seem to stick in my head very well.

I think it's working and your example is wrong. Your example says:

1. Start at ZOOM -2
2. Wait for 2 seconds but don't change ZOOM
3. By T3000 get to ZOOM -2 (it's already at ZOOM -2)
4. By T 3200 get to ZOOM 4
5. By T 4700 get to ZOOM 7

Also, STOP and LOOP commands at the end of a series of waypoints seem to be not working, unless I'm doing something else wrong.

Yes that's new behaviour. STOP and LOOP are now per Waypoint or POI. It actually doesn't make sense to have STOP and LOOP per Waypoint but under the covers Waypoints and POIs use the same code. In order to set initial STOP and LOOP you have to specify it before the first Waypoint (i.e. [[ PAUSE ]] or [[ T ]] command).

So for your example it would need to be written like this:

Code: Select all

x = 761, y = 777, rule = B3/S23
2o$2o4$3o$o$bo9$11b3o$11bo$12bo8$13b2o$12b2o$14bo5$13b3o$13bo$14bo$31b
3o$31bo$32bo39$75b2o$74b2o$76bo2$80b2o$79b2o$81bo11$59b2o29b2o$58b2o
29b2o$60bo30bo11$99b2o$98b2o$100bo$113b2o$112b2o$114bo21$144b2o$119b2o
22b2o$118b2o25bo$120bo$113b2o$112b2o$114bo8$128b2o$127b2o$129bo3$117b
2o$116b2o$118bo24b2o$142b2o$144bo2$133b2o$132b2o$134bo7$155b2o$154b2o$
156bo10$165b3o$165bo$166bo4$165b2o$164b2o$166bo8b2o$174b2o$176bo13$
193b2o$192b2o$194bo2$196b3o$196bo$197bo8$209b3o$209bo$210bo4$217b3o$
217bo$218bo2$207b3o$207bo$208bo23b3o$232bo$213b3o17bo$213bo$214bo$203b
2o$202b2o$204bo29b3o$234bo$224b3o8bo$224bo$225bo$236b2o$214b2o19b2o$
213b2o22bo$215bo8$240b2o$230b2o7b2o$229b2o10bo$231bo11$228b2o$227b2o$
229bo14$246b2o$245b2o$247bo36$266b3o$266bo$267bo8$279b3o$279bo$280bo5$
294b3o$294bo$295bo3$291b2o$290b2o$292bo21$319b3o$319bo$320bo9$313b3o$
313bo$314bo14b3o$329bo$330bo3$320b3o$320bo$321bo2$338b3o$338bo$339bo5$
353b3o$353bo$354bo9$378b2o$377b2o$365b3o11bo$365bo$366bo8$380b3o$380bo
$381bo5$374b3o$374bo$375bo2$392b3o$369b2o21bo$368b2o23bo$370bo6$384b2o
$383b2o$385bo7$376b2o$375b2o$377bo$413b2o$412b2o$414bo$417b3o$417bo$
418bo2$414b2o$413b2o$415bo3$470b2o$393b2o74b2o$392b2o77bo$394bo5$427b
3o$427bo$428bo3$479b2o$438b2o38b2o$437b2o41bo$439bo2$442b2o$441b2o$
443bo3$495b2o$490b2o2b2o$489b2o5bo$491bo10$517b2o$516b2o$518bo13$512b
3o$512bo$513bo3$434b3o93b2o$434bo94b2o4b2o$435bo95bo2b2o$536bo4$507b3o
$507bo$508bo3$502b2o$501b2o$503bo5$463b2o$462b2o52b3o$464bo51bo$517bo
9$528b3o$528bo$529bo$521b2o$483b3o34b2o$483bo38bo$484bo3$488b2o$487b2o
$489bo44b2o$482b2o49b2o10b2o6b3o$481b2o52bo8b2o7bo$483bo62bo7bo8$498b
2o$497b2o$499bo7b2o$506b2o$508bo48b3o$557bo7b3o$558bo6bo$566bo2$572b2o
$571b2o$573bo2$519b2o$518b2o66b3o$520bo56b2o7bo$530b2o44b2o9bo$529b2o
47bo$531bo2$579b3o$579bo26b2o$580bo24b2o$607bo5$605b3o$605bo$554b2o50b
o$553b2o$555bo6$618b3o$618bo$619bo6$621b3o$621bo$622bo$629b3o$629bo$
567b2o61bo$566b2o$568bo55b3o$624bo$625bo3$566b2o$565b2o$567bo2$645b3o$
645bo$646bo3b3o$650bo$651bo12$670b3o$670bo$671bo125$758b2o$758bobo$
758bo!
#C [[ THUMBNAIL THUMBSIZE 2 AUTOSTART STEP 5 ZOOM -2 STOP 4200 ]]
#C [[ PAUSE 2 LINEAR ZOOM HEIGHT 600 ]]
#C [[ T 3000 X -350 Y -350 ZOOM 2 LINEAR ZOOM ]]
#C [[ T 3200 X -350 Y -350 ZOOM 4 LINEAR ZOOM ]]
#C [[ T 4000 X -425 Y -425 ZOOM 7 ]]

Now I'm undecided with STOP and LOOP whether to either:

• Force script writers to set initial STOP and LOOP before the first Waypoint command and make adding STOP or LOOP to a Waypoint a script error. This would be consistent with POI behaviour but I guess would break a (very few) existing Waypoint animations.
  
  or:
  
  
• Make a STOP or LOOP in a Waypoint definition define the initial STOP and LOOP.

Thoughts?

[dvgrn]

I think it's working and your example is wrong.

Hm. You're right. Not sure what I was thinking. Hopefully I've gotten the confusion out of my system for another month or two.

Now I'm undecided with STOP and LOOP whether to either:

• Force script writers to set initial STOP and LOOP before the first Waypoint command and make adding STOP or LOOP to a Waypoint a script error...
  or:
  
• Make a STOP or LOOP in a Waypoint definition define the initial STOP and LOOP.

Thoughts?

Either one is fine by me. Every now and then I go back to old animations on the forums, and occasionally post a fix to an outdated script. Probably I'd find any broken scripts before anyone really noticed.

However, if there's a reasonably valid interpretation of a (single) STOP or LOOP command and it's just as easy to not throw an error, then I don't really see any reason to throw an error.

EDIT: The POPUPWIDTH / POPUPHEIGHT changes look good to me. Haven't tried the GRID OFF or AUTOSTART OFF yet -- maybe I'll wait for the next build (?) And what about STARS OFF ?

I've actually tried figure out how to do GRID OFF and STARS OFF before, inside a waypoint script. Wasn't terribly disappointed when I couldn't do STARS OFF, but since you seem to be heading in that direction anyway, maybe now's the time to mention it.

[rowett]

I'll get STARS OFF and GRID OFF working per Waypoint and then do a new build.

[dvgrn]

Hmm, there's an accidental LifeViewer bug report in Accidental Discoveries.

LifeViewer seems to be doing something different with a P25,25 bounded grid than Golly does. Looks like LifeViewer is centering the pattern correctly, but Golly is just dropping it in the upper left corner where the twin-bees effect just happens to work.

[dvgrn]

Huh, this is a little awkward. The way that templates currently work on the LifeWiki, the default settings are showing up after the settings that are supposed to override them. So we ended up with the following on the 2-engine Cordership page.

It wasn't too good anyway, because it was based on my slightly broken original experiment instead of the correction you suggested above. I'll make a few changes so it looks right on the wiki for now, and then see what we can do about the templates. Maybe a viewerconfig line is really the right way to go after all.

But... why does Build 239 give a "WIDTH 800 argument out of range" here on the forums, but not on the LifeWiki? EDIT Found it, never mind -- 4.3 For the conwaylife.com forum the meta tag doesn't exist so all Viewers are limited to the width of the HTML element containing their RLE. Why? It stops Viewers escaping out of the central column.

Also, what do I do if I want to cancel the default THUMBLAUNCH?

An option we don't currently have is playing the animation but keeping the viewer stuck at a fixed NOGUI thumbnail size, right? I suppose it would be kind of rude to lock things down like that.

Code: Select all

#N 2-engine Cordership, slow salvo construction of 1-glider seed
#O Dave Greene, 2018
#C http://conwaylife.com/forums/viewtopic. ... 674#p57674
#C http://conwaylife.com/wiki/2-engine_Cordership
x = 761, y = 777, rule = B3/S23
2o$2o4$3o$o$bo9$11b3o$11bo$12bo8$13b2o$12b2o$14bo5$13b3o$13bo$14bo$31b
3o$31bo$32bo39$75b2o$74b2o$76bo2$80b2o$79b2o$81bo11$59b2o29b2o$58b2o
29b2o$60bo30bo11$99b2o$98b2o$100bo$113b2o$112b2o$114bo21$144b2o$119b2o
22b2o$118b2o25bo$120bo$113b2o$112b2o$114bo8$128b2o$127b2o$129bo3$117b
2o$116b2o$118bo24b2o$142b2o$144bo2$133b2o$132b2o$134bo7$155b2o$154b2o$
156bo10$165b3o$165bo$166bo4$165b2o$164b2o$166bo8b2o$174b2o$176bo13$
193b2o$192b2o$194bo2$196b3o$196bo$197bo8$209b3o$209bo$210bo4$217b3o$
217bo$218bo2$207b3o$207bo$208bo23b3o$232bo$213b3o17bo$213bo$214bo$203b
2o$202b2o$204bo29b3o$234bo$224b3o8bo$224bo$225bo$236b2o$214b2o19b2o$
213b2o22bo$215bo8$240b2o$230b2o7b2o$229b2o10bo$231bo11$228b2o$227b2o$
229bo14$246b2o$245b2o$247bo36$266b3o$266bo$267bo8$279b3o$279bo$280bo5$
294b3o$294bo$295bo3$291b2o$290b2o$292bo21$319b3o$319bo$320bo9$313b3o$
313bo$314bo14b3o$329bo$330bo3$320b3o$320bo$321bo2$338b3o$338bo$339bo5$
353b3o$353bo$354bo9$378b2o$377b2o$365b3o11bo$365bo$366bo8$380b3o$380bo
$381bo5$374b3o$374bo$375bo2$392b3o$369b2o21bo$368b2o23bo$370bo6$384b2o
$383b2o$385bo7$376b2o$375b2o$377bo$413b2o$412b2o$414bo$417b3o$417bo$
418bo2$414b2o$413b2o$415bo3$470b2o$393b2o74b2o$392b2o77bo$394bo5$427b
3o$427bo$428bo3$479b2o$438b2o38b2o$437b2o41bo$439bo2$442b2o$441b2o$
443bo3$495b2o$490b2o2b2o$489b2o5bo$491bo10$517b2o$516b2o$518bo13$512b
3o$512bo$513bo3$434b3o93b2o$434bo94b2o4b2o$435bo95bo2b2o$536bo4$507b3o
$507bo$508bo3$502b2o$501b2o$503bo5$463b2o$462b2o52b3o$464bo51bo$517bo
9$528b3o$528bo$529bo$521b2o$483b3o34b2o$483bo38bo$484bo3$488b2o$487b2o
$489bo44b2o$482b2o49b2o10b2o6b3o$481b2o52bo8b2o7bo$483bo62bo7bo8$498b
2o$497b2o$499bo7b2o$506b2o$508bo48b3o$557bo7b3o$558bo6bo$566bo2$572b2o
$571b2o$573bo2$519b2o$518b2o66b3o$520bo56b2o7bo$530b2o44b2o9bo$529b2o
47bo$531bo2$579b3o$579bo26b2o$580bo24b2o$607bo5$605b3o$605bo$554b2o50b
o$553b2o$555bo6$618b3o$618bo$619bo6$621b3o$621bo$622bo$629b3o$629bo$
567b2o61bo$566b2o$568bo55b3o$624bo$625bo3$566b2o$565b2o$567bo2$645b3o$
645bo$646bo3b3o$650bo$651bo12$670b3o$670bo$671bo125$758b2o$758bobo$
758bo!
#C [[ THUMBNAIL THUMBSIZE 2 STEP 5 PAUSE 2 LINEAR ZOOM HEIGHT 600 WIDTH 800 ]]
#C [[ T 100 X -360 Y -350 ZOOM 4 ]]
#C [[ T 3200 X -360 Y -350 ZOOM 6 ]]
#C [[ T 4000 X -435 Y -425 ZOOM 7 ]]
#C [[ STOP 4200 ]]
#C [[ THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]]

[rowett]

Hmm, there's an accidental LifeViewer bug report in Accidental Discoveries.

LifeViewer seems to be doing something different with a P25,25 bounded grid than Golly does. Looks like LifeViewer is centering the pattern correctly, but Golly is just dropping it in the upper left corner where the twin-bees effect just happens to work.

Golly is respecting the "x = 25, y = 25" definition, whilst LifeViewer ignores it and computes the x and y from the actual RLE. Both then center the pattern but Golly does it based on a 25 x 25 pattern a LifeViewer based on what it computed from the RLE.
I'm not sure which is "correct". It's actually unusual for the x and y definitions to be different than the pattern size which is probably why this wasn't spotted before.

Thoughts?

[rowett]

Also, what do I do if I want to cancel the default THUMBLAUNCH?

I'll need to implement THUMBLAUNCH OFF. It's on the backlog.

An option we don't currently have is playing the animation but keeping the viewer stuck at a fixed NOGUI thumbnail size, right? I suppose it would be kind of rude to lock things down like that.

Yes currently LifeViewer assumes NOGUI is for static images and specifically ignores AUTOSTART.

[dvgrn]

I'm not sure which is "correct". It's actually unusual for the x and y definitions to be different than the pattern size which is probably why this wasn't spotted before.

Thoughts?

This has been a thorny question for a long time, mostly because Life32v2.16 had a really annoying bug in it where you would copy out a selection and it would show up with zeroes for the X and Y bounds, or even negative numbers. So it's not really a good idea to have the standard that Golly used to have, that RLE patterns are clipped to their reported bounding boxes.

It also happens somewhat regularly that the X and Y values are a bit too small -- e.g., for programmatically generated RLE where the header line is just hard-coded as "x = 999, y = 999" or some such.

On the other hand, it's pretty useful to be able to use RLE to specify the size of the selection box as well as the pattern itself. Especially leading $ lines and leading b's on every line probably shouldn't be ignored, because they might be there for a reason. (That's different from leading tabs or spaces before every line of ASCII patterns, which _should_ probably be ignored as we've previously established...!) Space at the top or left of RLE patterns allows another way besides a #CXRLE Pos= header for chunks of pattern to be aligned -- every piece can be dropped in at (0,0) and yet everything ends up in the right relative locations.

So... I guess if Golly is doing something sensible with this unusual variety of RLE, then it probably makes sense to do what Golly does.

[rowett]

So... I guess if Golly is doing something sensible with this unusual variety of RLE, then it probably makes sense to do what Golly does.

Yep that's usually the answer :)

As for how "sensible" it is...

[rowett]

Build 244 is now available on the lazyslug server

Enhancements in this build:

• added [[ STARS OFF ]] script command
• added [[ THUMBNAIL OFF ]] and [[ THUMBLAUNCH OFF ]] script commands
• added [[ AUTOFIT OFF ]], [[ HISTORYFIT OFF ]] and [[ STATE1FIT OFF ]] script commands
• both Stars and Grid display can be defined per POI (but not yet per Waypoint)
• pattern actual size vs specified size shown in Help information

Fixes in this build:

• fixed TRACKLOOP that had stopped looping
• fixed pattern position in bounded box when specified pattern size is not actual size
• reverted so LOOP and STOP definitions not at POIs change the initial settings